Health and Memory Threshold Updates

NOTE: This is for 10.12 and beyond.

For our 10.12 release, we have updated six default health category thresholds that make up the SysTrack Health Score, to be more relevant for modern customer environments, and the systems they run.

The following are the new default health thresholds with their new values:

Category	Metric	Value
CPU	CPU Percentage	90%
Hardware	Hardware Interrupt Rate	>10%
Latency	Latency Gateway	>75ms
	Home Directory	>100ms
	Latency Sessions	>200ms
Memory	Memory Available	<20%
Network	Network Retransmit Rate	>5%
	Network Utilization	>70%
Virtual Machine	Virtual Machine Ready Time	>5%

With the prevalence of remote working and dynamic office environments, we are also including Wi-Fi, which has been requested by many customers, as a key system health metric.

• Wi-Fi Signal strength is included in the Network health category, the default threshold for impact is set at <50%.

We are also updating Session Latency for the ICA protocol to reference RTT (round trip time).

How will this affect my environment?

Once 10.12 is applied to your cloud environment, the new thresholds will be applied to all of your agents.

NOTE: If you have custom health thresholds set to roles and applied to configurations, they will take precedence over the new thresholds.

Memory Threshold

With the 10.12 release, the memory thresholds have changee from an absolute value to a percentage.

Scenario	Result
Master and agent are upgraded to 10.12, no config set for Available Memory.	Agent uses new default memory percentage (<20%).
Master and agent are upgraded to 10.12, configuration of Available Memory (absolute bytes) is set.	Agent uses default memory percentage (<20%) since internally it is a different config from the absolute memory (bytes).
Master upgrades to 10.12 and agent remains on older version with no config set for Available Memory (absolute bytes).	Agent will operate the same as if the master didn't upgrade since the percentage is a new value. Check is based on absolute memory value.
Master upgrades to 10.12 and agent remains on older version with Available Memory config for absolute (bytes) value set.	Agent will operate the same as if the master didn't upgrade since the percentage is a new value. Check is based on absolute memory value.

As agents are upgraded to 10.12 on your systems, Wi-Fi signal strength will impact health if it is below the threshold set. The threshold can be customized per role, which is the same way as existing health thresholds. This threshold can be set in advance of the agent being updated on systems.

Health scores will be affected by the new thresholds, so you may see some changes to overall estate health and per device.

Opt Out of the 10.12 Update to Health Thresholds

If you do not want to update to the changes in 10.12, you can apply per role health values to your systems using the old values. This needs to be done prior to the cloud release of 10.12.

IMPORTANT: Customized thresholds will not be overwritten.